Skip to content

Fix tailor validation rejecting company in subtitle field#71

Open
ArchieChelle wants to merge 2 commits into
Pickle-Pixel:mainfrom
ArchieChelle:fix/tailor-validator-company-subtitle
Open

Fix tailor validation rejecting company in subtitle field#71
ArchieChelle wants to merge 2 commits into
Pickle-Pixel:mainfrom
ArchieChelle:fix/tailor-validator-company-subtitle

Conversation

@ArchieChelle

Copy link
Copy Markdown

Problem

The resume tailor's Layer 1 validator (validate_json_fields in scoring/validator.py) was rejecting valid tailored resumes with Company 'X' missing from experience, even when the company was present.

Root cause: the preserved-company check only inspected each experience entry's header field. But the tailor prompt's JSON schema lets the LLM place the company in either the header ("Title at Company") or the subtitle ("Company | Dates"). When the LLM chose the subtitle, the check failed and the whole resume was rejected as a fabrication/omission.

Observed impact: 19 of 20 tailored resumes in a run failed validation for this reason.

Fix

Check the company name against both header and subtitle when verifying preserved companies are present. After the fix, 16–19 of 20 pass.

Scope

One-line logic change in validator.py. No schema or prompt changes.

ArchieChelle and others added 2 commits June 25, 2026 00:35
The preserved-company check in validate_json_fields only looked at each
experience entry's `header` field. The LLM reliably places the role in
`header` and the company in `subtitle` (e.g. "First Family Trust | Dates"),
so the check failed for every company on nearly every job, causing ~95% of
tailored resumes to be rejected as FAILED_VALIDATION after exhausting all
retries.

Check the company name against both `header` and `subtitle` so legitimately
formatted output passes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant